-
Notifications
You must be signed in to change notification settings - Fork 3.3k
fix(bigquery): pass graph client to lineage extractor to prevent missing lineage from unresolved schemas #15137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
+87
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
…ing lineage from unresolved schemas 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
|
These new insights documented in #15164 invalidate the work in this PR, as it was going in a wrong direction. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes a critical issue where BigQuery SQL lineage parsing was failing to generate lineage relationships due to missing graph client, causing schema resolution failures during SQL parsing.
Root Cause: The BigQuery lineage extractor was not receiving the DataHub graph client, preventing it from resolving table schemas that exist in DataHub but are not in the current ingestion cache. This resulted in
"Resolved 0 of X table schemas"log traces and missing upstream lineage for datasets.Changes Made:
SqlParsingAggregatorSchemaResolveris initialized without a graph client